MULTIARCH-3965: Check if PER is enabled in the target PowerVS workspace#7683
Conversation
106c9ab to
7b81ab5
Compare
|
/retest-required |
|
Closes MULTIARCH-3965 |
|
/lgtm |
|
FYI and not a review, but fix the golint errors |
7b81ab5 to
47286fe
Compare
|
/retest-required |
47286fe to
78148ac
Compare
|
/retest-required |
2 similar comments
|
/retest-required |
|
/retest-required |
815d742 to
ab43837
Compare
|
/retest-required |
1 similar comment
|
/retest-required |
There was a problem hiding this comment.
Also here? At least mention that it is in GetDatacenterCapabilities?
There was a problem hiding this comment.
Addressed in the latest force-push. PTAL.
There was a problem hiding this comment.
ServiceInstanceID is going away in my PR. Let's not introduce it again.
|
/retest-required |
9740bca to
ff28556
Compare
ff28556 to
c9705ea
Compare
|
/retest-required |
There was a problem hiding this comment.
Doesn't need to be addressed in this PR, but maybe powervs can follow the pattern of the other platforms and use a ValidateForProvisioning function that encapsulates all the different validations needed.
There was a problem hiding this comment.
Could "power-edge-router" not show up in the set of capabilities? If so, maybe it's better to separate the error types (i.e. "capability not found" vs "capability not available")?
There was a problem hiding this comment.
Addressed in the latest force-push. PTAL.
c9705ea to
e4287c9
Compare
There was a problem hiding this comment.
For completeness, a test case where "power-edge-router" is not available.
There was a problem hiding this comment.
Addressed in the latest force-push. PTAL.
|
Jira issues are now required in all PRs. |
Signed-off-by: Hiro Miyamoto <miyamotoh@us.ibm.com>
e4287c9 to
196d7d2
Compare
|
@miyamotoh: This pull request references MULTIARCH-3965 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: r4f4 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
/retest-required |
1 similar comment
|
/retest-required |
|
/retest-required |
|
/test openstack-manifests |
|
We cannot get |
Yes. See the fix at #7617 |
|
@miyamotoh: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Power Edge Router (aka. "PER") needs to be enabled in the target region to connect PowerVS to VPC, and thus is required for IPI to proceed. Hence this new validation check before doing anything substantial with Terraform.
Signed-off-by: Hiro Miyamoto miyamotoh@us.ibm.com